Systems and methods for building applications using building blocks linkable with metadata

ABSTRACT

Systems and methods relate to creating applications using building blocks linked together with metadata. A user interface can enable a user to create an application. Creating the application can include defining a new building block configured to generate output data. The new building block can include one or more existing building blocks and the metadata associated with the existing building blocks. For example, a building block can include at least one input/output (I/O) feature configured to receive inputs and/or generate outputs. Further, the existing building block can correspond to a data structure including external I/O features. The new building block can be linked to an existing building block by mapping an external I/O feature of the existing building block to an open I/O feature of the new building block. The mapping can be stored in metadata associated with the new building block.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of U.S. ProvisionalApplication No. 62/395,892, filed on Sep. 16, 2016, the disclosure ofwhich is herein incorporated by reference in its entirety for allpurposes.

FIELD

The present disclosure relates generally to building applications. Morespecifically, the present disclosure relates to building applicationsusing building blocks that are linkable with customizable metadata.

BACKGROUND

Generally, users have increasingly been customizing applications createdby application providers (e.g., applications created by PEOPLESOFT™).However, customizations performed by users are problematic. Forinstance, if the application is modified by the application provider(e.g., upgraded or patched), the customizations performed by the user tothe application are overridden. Users often generate and review reportsto determine how the look and feel has changed or other customizedsettings have been lost after the application is modified. Users mayhave to re-customize the application to achieve the look and feel andcustomized settings they prefer. This process can be very complex andburdensome due to the number of changes in the customization.

SUMMARY

Certain aspects and features of the present disclosure relate to systemsand methods for creating applications using building blocks that can belinked together with metadata. In one embodiment, a user interface canbe provided to enable a user to create an application. Creating theapplication can include defining a new building block configured togenerate output data. To generate the output data, the new buildingblock can include one or more existing building blocks and the metadataassociated with the existing building blocks. For example, a buildingblock can include a portion of code (e.g., executable logic) thatcorresponds to at least one input/output (I/O) feature configured toreceive inputs and/or generate outputs. Further, the building block cancorrespond to a data structure including external I/O features. Theexternal I/O features can include inputs that are defined for storage tothe data structure and/or outputs that are defined for retrieval fromthe data structure. The new building block can be linked to an existingbuilding block by mapping an I/O feature of the existing building blockto an open I/O feature of the new building block. The mapping can bestored in metadata associated with the new building block, such thatwhen the new building block is accessed at a later time, the metadataindicates that the open I/O feature is linked to the I/O feature of theexisting building block.

In another embodiment, the I/O features of previously defined buildingblocks can be selectable from a menu object (e.g., a drop down menu).For example, the menu object can be dynamically generated in response toa detection of a request to build a new building block. In response todetecting the request, the menu object can display a list of existingbuilding blocks, such that the I/O features of the displayed buildingblocks are the types of I/O features that are compatible with the openI/O feature of the new building block. The list of existing buildingblocks displayed can be dynamically updated (e.g., each time a list isrequested for use in building a new building block or connecting to anexisting building block, the list is determined by determining, at thattime, a collection of then-available building blocks and/or their I/Ofeatures and populating the list based on the collection), such that thelist of previously-defined building blocks grows as more building blocksare defined. For example, the new building block, along with themetadata associated with the new building block, becomes available forselection using the menu object when the new building block isregistered.

In another embodiment, the building blocks may be called as web services(e.g., a representational state transfer (REST) service) that can beinteracted with either inside of a building block architecture oroutside of the building block architecture using exposed protocols. AREST service is an architectural style for networked applications. Forexample, the building block can be combinable with other building blockswithin the building block architecture that exposes one or moreparticular other building blocks that are not exposed using webservices. In this embodiment, a building block can be transformed into amachine-readable description language (e.g., a web applicationdescription language (WADL), a web service description language (WSDL),etc.) that can be modified and/or called using a URI. In an embodiment,the building block architecture can include a PEOPLESOFT™ platform.

In another embodiment, a single-click user interface (UI) tool (e.g., acheckbox feature) can be provided on the user interface. Thesingle-click UI tool can facilitate toggling between unselected andselected based on a single item of user input (e.g., a single click, asingle tap, a single swipe, or a single keypress) received at a buildingblock configuration interface. In some instances, the toggling causesswitching between customization modes. For example, in a first mode(e.g., when the checkbox feature is unselected), the rendering objectassociated with an existing building block is executed at runtimewithout executing any customized metadata. In this example, when in thefirst mode, the delivered application without any customizations isexecuted at runtime. In some instances, the toggling causes switchingbetween using another building block and then customizing based onmetadata on top of a (single) rendering object (customized withmetadata) (e.g., a first mode), or copying another building block andcreating a custom building block that generates its own rendering object(natively custom) (e.g., a second mode), when referencing an existingbuilding block from a new building block. In some instances, a deliveredapplication can correspond to an original application class created bythe application provider. A user can customize the delivered applicationby creating a new application class, which includes customized metadatato be applied to the delivered application. In these instances, atruntime, the output data and the associated metadata that is generatedfrom executing the original application class is stored as a renderingobject and is used as input to the new application class.Advantageously, the output data and the associated metadata generatedfrom the original application class can be selectively customized (e.g.,overridden) by metadata of the new application class without modifyingthe original application class or metadata of the delivered application.As only a non-limiting example, if executing the original applicationclass generates a table of 20 columns and 4 rows, the new applicationclass can be coded to select some or all of the data in the table or toextend the table to 25 columns. In this example, the metadata includedin the new application class can override the metadata stored in therendering object (from the original application class). In someinstances, only the new application class is executed. In theseinstances, when a particular mode is selected by the user, the originalapplication class is not executed, but rather, only the new applicationclass is executed, thereby generating the data structure coded in thenew application class. It will be appreciated that an application classcan be associated with an event (e.g., a save event, an initializationevent, etc.). It will further be appreciated that the selectiveexecution of (1) the original application class followed by the newapplication class, or (2) only of the new application class, can be onan event-by-event basis.

In some embodiments, a computer-implemented method is provided. Themethod can include providing an interface configured to enable a user tobuild an application. For example, building the application can includelinking building blocks. The building blocks can be configured toprocess data from data structures. A first input can be received via theinterface, wherein the first input corresponds to a request to build anew building block. Further, the method can include adding one or moreI/O features to the new building block. For example, the one or moreopen I/O features can comprise one or more open inputs to the newbuilding block and/or one or more open outputs from the new buildingblock. A plurality of existing building blocks can be accessed. Eachexisting building block of the plurality of existing building blocks cancorrespond to a data structure comprising one or more external I/Ofeatures. For example, the one or more external I/O features cancomprise one or more inputs that are defined for storage to the datastructure and/or one or more outputs that are defined for retrieval fromthe data structure. The method can also include generating a menu objectthat facilitates a selection of one or more building blocks from amongstthe plurality of existing building blocks. An identifier of each of theone or more building blocks can be displayed when the menu object isselected. A second input corresponding to a selection, identified usingthe menu object, of a particular building block can be received. A thirdinput corresponding to a selection of a particular external I/O featureof the particular building block can be received. For example, the thirdinput can be received to add to a particular open I/O feature of the newbuilding block. The method can also include assigning the particularexternal I/O feature of the particular building block to the particularopen I/O feature of the new building block. The assigning can includestoring assignment metadata in association with the new building block.Further, the assignment metadata can indicate a link from the particularexternal I/O feature to the particular open I/O feature. For example,either an input of the particular building block can be mapped to anoutput of the new building block or an output of the particular buildingblock can be mapped to an input of the new building block. Thedefinition of the new building block can be stored. The definition cancomprise the one or more open I/O features and the assignment metadata.

In some embodiments, another computer-implemented method is provided.The method can include accessing a plurality of existing buildingblocks. Each existing building block of the plurality of existingbuilding blocks can correspond to a web service associated with auniform resource identifier (URI). Further, each existing building blockcan correspond to a data structure configured to receive an input andgenerate an output using executable logic. A building block from amongstthe plurality of existing building blocks can be identified. Thebuilding block can be transformed into a machine-readable descriptionlanguage that includes at least one input parameter and a representationof the output associated with the building block. Further, the webservice that corresponds to the building block can be invoked. Forexample, the invocation of the web service can include calling the URIassociated with the web service. The calling of the URI can cause the atleast one input parameter to pass through the building block, such thatthe output is generated. A communication corresponding to the output ofthe building block can be received. The output can be represented inaccordance with the representation of the output included in themachine-readable description language. The building block may also beaccessible as a building block that can be combined with other buildingblocks within a building block architecture that also exposes one ormore particular other building blocks that are not exposed using webservices.

In some embodiments, another computer-implemented method is provided.The method can include providing an interface to enable a user to definea customization setting of building blocks. The method can includeidentifying an application class associated with an existing buildingblock. For example, the application class ca be associated with one ormore rendering objects. The application class can also correspond toexecutable logic. Further, the method can include identifying a newapplication class associated with a new building block corresponding tothe existing building block. The new application class can be associatedwith one or more new rendering objects. The new application class canalso correspond to new executable logic including customized metadata.An item of user input (for example, a single click, a single tap, asingle swipe, or a single keypress) can be received at a building blockconfiguration interface that facilitates a selection. For example, theuser input can correspond to a selection of a selectable feature. Thestate of the selectable feature can define the customization setting forthe new building block. The selection of the selectable feature cancause the state of the selectable feature to be modified between a firstmode and a second mode, and vice versa. In response to receiving theuser input, mode metadata associated with the new building block can begenerated and stored. The mode metadata can correspond to a first modein association with the new building block if the first mode isselected, or a second mode in association with the new building block ifthe second mode is selected can be processed. If the second mode isselected, responsive to receiving the input, a copy of the one or morerendering objects can be stored in association with the new buildingblock. The method can include receiving a request to execute the newbuilding block. In response to receiving the request, the method caninclude determining whether the mode metadata corresponds to the firstmode or the second mode. When the mode metadata corresponds to the firstmode, the application class can be called, such that the customizedmetadata associated with the new building block is applied to the one ormore rendering objects. When the mode metadata corresponds to the secondmode, the new application class can be called, such that the customizedmetadata associated with the new building block is applied the copy ofthe one or more rendering objects that was stored responsive toreceiving the input.

In some embodiments, a computer-program product is provided that istangibly embodied in a non-transitory machine-readable storage medium.The computer-program product can include instructions configured tocause one or more data processors to perform part or all of a methoddisclosed herein. In some embodiments, a system is provided. The systemcan include one or more data processors and a non-transitory computerreadable storage medium containing instructions which, when executed onthe one or more data processors, cause the one or more data processorsto perform part or all of a method disclosed herein.

Advantageously, new applications can be built and/or existingapplications can customized without changing the metadata of theunderlying original application. Further, any changes made to themetadata of the original application (e.g., in an update or a patch)would not override metadata associated with new or customizedapplications.

The following detailed description together with the accompanyingdrawings will provide a better understanding of the nature andadvantages of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the following drawing figures:

FIG. 1 shows an example network for controlling resource access andoperation across sub-systems and/or systems.

FIG. 2 shows a simplified block diagram of components of an application.

FIG. 3 is a flowchart illustrating a process for building anapplication.

FIG. 4 is a flowchart illustrating a process for calling building blocksas web services.

FIG. 5 is a flowchart illustrating a process for customizingapplications.

FIG. 6 shows an example interface for building an application usingbuilding blocks.

FIG. 7 shows an example interface for mapping primitives to datastructures of building blocks.

FIG. 8 shows an example interface for building an application usingcontainers.

FIG. 9 shows an example interface for customizing metadata associatedwith the containers shown in FIG. 8.

FIG. 10 depicts a simplified diagram of a distributed system forimplementing one of the embodiments.

FIG. 11 is a simplified block diagram of components of a systemenvironment by which services provided by the components of anembodiment system may be offered as cloud services, in accordance withan embodiment of the present disclosure.

FIG. 12 illustrates an exemplary computer system, in which variousembodiments of the present invention may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

FIG. 1 shows an example network 100 for controlling resource access andoperation across sub-systems and/or systems. Network 100 includessystems corresponding to multiple clients and to multiple locations.More specifically, each of on-site client 1 system 102, virtual clientsystem 106 and client 2 system 104 can correspond to a set of devicesand/or other components, such as one or more servers (e.g., and/orserver farms or server clusters), user devices (e.g., desktop computers,laptops, tablets, or smart phones), data storage devices (e.g.,network-attached storage), and/or equipment. The set of devices and/orother components can, in some instances (e.g., for on-site client 1system), be co-located, such as being located within one or morebuildings or geographical areas associated with the client. In someinstances, the clients need not be co-located but are connected via anetwork (e.g., a private network). In instances where different parts ofa given client's system are at different locations (e.g., part being atan on-site location and part being virtual), the systems may communicatevia a network, such as a WiFi network 108.

A system can include multiple sub-systems. Each of the multiplesub-systems may (for example) be configured to perform a different typeof operation, to use different resources (and/or different types ofresources), to generate different types of outputs, to be located atdifferent geographical locations, to correspond to (e.g., to grantaccess to) different agents or users (e.g., to different departments ofan organization), and so on. For example, on-site client system 102 caninclude a first sub-system 110 and a second sub-system 112. Firstsub-system 110 can be configured to receive and respond to requests fromuser devices for content, and second sub-system 112 can be configured todynamically monitor and re-configure network resources. First sub-system110 and second sub-system 112 may communicate via WiFi network 108 or alocal area network 114. Each of first sub-system 110 and secondsub-system 112 can further communicate with a sub-system coordinationresource 116. Sub-system coordination resource 116 may process data fromeach of one or more sub-systems to (for example) determine whetheroperation at one sub-system is consistent with operation at anothersub-system or with system-level policies and/or to determine how one ormore resources are to be allocated to a sub-system.

The implementation depicted in FIG. 1 illustrates various types ofresources of systems. It will be appreciated that these resources areillustrative. Resources represented by separate blocks may, but neednot, correspond to separate devices or groups of devices.

In the depicted instance, first sub-system 110 includes a contentmanagement resource 118, which is configured to query one or more datastores for content responsive to content requests and to transmitresponses to content requests. For example, content management resource118 may be configured to receive HTTP requests from a user device 119and respond with webpage data. First sub-system 110 can further includea security resource 120, which may be configured to determine what datavarious users are authorized to receive and/or what types of actionsvarious agents are authorized to make. For example, security resource120 may receive or intercept a request from an agent device 122 to addor modify data in a content data store (e.g., stored locally at firstsub-system 110 or remotely) and to determine whether such an addition ormodification is allowed (e.g., based on an authentication of agentdevice 122 and/or information associated with the request).

First sub-system 110 also includes a processing resource 124, which canbe configured to perform data processing, such as processing retrievedcontent (e.g., to convert it from a first to a second format oridentifying particular content objects to retrieve in response to arequest). First sub-system 110 further includes a scheduling resource126, which may monitor incoming requests and identify when each requestis to be processed (e.g., by managing a request queue).

Second sub-system 112 includes a performance monitor resource 128, whichmay assess a data log corresponding to requests being handled by firstsub-system 110. The assessment may include monitoring a speed at whichthe requests are processed and an error rate. Results of the assessmentcan be transmitted to another agent device 130. A network configuringresource 132 can initiate various reconfigurations that may influenceperformance, such as server allocation. A reconfiguration may beautomatically performed or performed responsive to a request from managent device, such as agent device 130. An agent-initiatedreconfiguration may require an authorization of the agent or agentdevice.

Client 2 system 104 includes an equipment resource 134 that may beconfigured to generate outputs. For example, equipment resource 134 may(for example) process inputs (e.g., parts, materials and/or input data)to generate a tangible product (e.g., a manufactured or assembled part)or intangible result (e.g., quantitative characterization of a sample orpart, biological metric, environmental data, wireless signalcharacteristics, and so on). A sensor resource 136 can be configured togenerate readings corresponding to an operation of equipment resource134, such as an operating temperature and/or energy being used. Aprocessing resource 138 can send instruction communications to equipmentresource 134, which can control an operation of the equipment resource(e.g., to define inputs, identify types of processing and/or indicatewhen the resource is to operate). Processing resource 138 may determinesuch instructions in response to processing requests for particularoutputs. Processing resource 138 may further or alternatively assessdata corresponding to operation of equipment resource 134 (e.g.,characteristics of output data, efficiency of product and/or sensorreadings) to determine whether an alert condition is satisfied. In someinstances, processing resource 138 operates so as to schedule operationsat one or more equipment resources 134, schedule request processingand/or coordinate process control (e.g., via assessment of sensormeasurements).

Agent device 140 may provide operation parameters and/or gain access todata. For example, an operation parameter may include or at least partlydefine a part of a workflow that is to occur (e.g., at least partly viaequipment resource 134) as part of a processing of a request. In someinstances, a local or remote security resource verifies that aparticular agent device or corresponding agent is authorized to providesuch parameters and/or gain access.

Virtual client system 106 includes various resources for a system thatare, for example, operating in the cloud. In some instances, part or allof virtual client system 106 is identified as being or being used for orby an on-site sub-system (e.g., first sub-system 110 and/or secondsub-system 112). A component may, but need not, be shared across two ormore sub-systems. In some instances, part or all of virtual clientsystem 106 corresponds to a separate sub-system from one, more or allon-site sub-systems. In some instances, virtual client system 106includes multiple sub-systems.

In the depicted instance, virtual client system 106 includes a datastorage resource 142, which may include databases and/or data stores fora client. The databases and/or data stores may be configured tofacilitate periodic updating and/or retrieving data in response toqueries generated and coordinated by a query resource 144. For example,a data store can include content objects managed by content managementresource 118, and query resource 144 can be configured to generate aquery for content objects from an external source (e.g., a source system146). As another example, a data store can include historicaloperational data of one or more equipment resources 134 for client 2system. As yet another example, a data store can include datacorresponding to requests for particular types of outputs of equipmentresource 134, such that queries of the data store (e.g., as performedusing query resource 144) can be used to control operation parameters ofequipment resource 134 to facilitate responsiveness to the requests.

A usage monitor resource 148 can generate data logs corresponding to(for example) incoming communications, internal system performance(e.g., of content retrieval or equipment operation) and/or systemcommunications. For example, usage monitor 148 can generate and maintaina data log assessed by performance monitor resource 128 based onmonitoring of requests and request responses processed by contentmanagement resource 118. As another example, usage monitor 148 cangenerate and maintain a data log of a quality metric and/or ofmaintenance events corresponding to equipment resource 134. As yetanother example, usage monitor 148 can generate and maintain a data logof sensor measurements collected by sensor resource 136.

Another security resource 150 can assess system access requests, usagepatterns, and/or system events to monitor for security threats. Forexample, a frequency, source and/or request content of content-objectrequests may be assessed. As another example, a data log is assessed todetermine whether any patterns, trends and/or log-element frequenciesare indicative of a security threat. As yet another example, securityresource 150 may monitor equipment operation or agent instructions todetermine whether any operations or instructions are atypical from oneor more characteristics of previous instructions or correspond tosatisfaction of an alert indication. When security resource 150 detectsa potential threat decision, it may trigger an alert to be transmittedto an agent device, such as agent device 122, agent device 140, or anexternal agent device 152.

An allocation resource 152 can control which cloud resources areallocated to a given client, client sub-system, task performance, and soon. For example, allocation resource 152 can control allocation ofmemory, data stores (e.g., network attached storage), processors, and/orvirtual machines.

FIG. 2 shows a simplified block diagram of components of an application.As illustrated in the example of FIG. 2, application 200 can be createdby a user. For example, the user can be a developer that interacts witha user interface to build or create the application. In some instances,the application can be executable on a browser that is running on a userdevice (e.g., a mobile device, a smart phone, a tablet computer, alaptop, a desktop, and electronic kiosk, and other suitable devices).Further, the application can be associated with a URI, such that whenthe application is called (e.g., by entering the URI into the browserrunning on the user device), the application can be executed (e.g.,rendered at run time).

In an embodiment, the user can build application 200 using the userinterface. The user interface can receive a request from the user tobuild new building block 205. For example, the user interface canreceive an input corresponding to a selection of a selectable feature(e.g., a button, link, etc.) that initiates a request to build a newbuilding block. A building block can include a portion of code (e.g.,executable logic) of an existing application, such that the portion ofcode is configured to receive inputs and generate outputs. Further, abuilding block can include a data structure that stores data of one ormore data types in records or databases (e.g., columns, rows, tables,lists, etc.). In an embodiment, the data structure can comprise one ormore external input/output (I/O) features. An external I/O feature caninclude an input that is defined for storage to the data structureand/or one or more outputs that are defined for retrieval from the datastructure. In some cases, a building block can be defined by input(s) orused value(s), if any; intermediate operation(s) based on the input(s)or other specified value(s) or setting(s); and/or any one or more of thefollowing output(s): data to be provided in-line directly to anotherconnected building block (pushed output); data stored in a datastructure to be made available to other building blocks (pullableoutput); interface configuration, interface configuration metadata;and/or interface content to be rendered on a part of the graphical userinterface to which the building block is plugged in. In some cases, thepushed output(s) and/or pullable output can be (or be associated with)an I/O feature of a building block.

New building block 205 can include one or more open I/O features. Forexample, an open I/O feature can include an unassigned (e.g., open)input to new building block 205 and/or an unassigned (e.g., open) outputto new building block 205. An open input can be an input that has notyet been linked to a source (e.g., a record, a database, an output of anexisting building block or application, etc.). Further, an open outputcan be an output that has not yet been linked to a destination (e.g., arecord, a database, an input of an existing building block orapplication).

The user can map existing I/O features from existing building blocks tothe open I/O features of new building block 205 using assignmentmetadata. For example, the user can select a particular existingbuilding block (e.g., building block 220) using a menu object (e.g., adrop down menu) as discussed below with respect to FIGS. 3-6. The usercan then map open I/O feature A to one of the I/O features of buildingblock 220 (e.g., the input of building block 220). As only anon-limiting example, building block 220 can be configured to receive auser input, such as a user identification (ID), an address, a phonenumber, or any other input entered by a user. While not shown in FIG. 2,open I/O feature A can also be mapped to an output of building block220. As only a non-limiting example, the output of building block 220can be a function that queries a database for additional informationassociated with the user ID (e.g., user groups, profile information,etc.).

Mapping an open I/O feature to an I/O feature of an existing buildingblock can include storing assignment metadata in association with newbuilding block 205. In an embodiment, the assignment metadata caninclude metadata that identifies that the open I/O feature iscontextually mapped to the input of building block 220. In anotherembodiment, the assignment metadata can include metadata that retrievesdata from a URI associated with the I/O feature of building block 220.For example, when the executable logic associated with new buildingblock 205 runs, the assignment metadata causes open I/O feature A to getor retrieve data from the assigned I/O feature of building block 220. Inthis example, the assigned I/O feature of building block 220 cancorrespond to a data structure that stores various records of data. Theassignment metadata can identify that open I/O feature is to retrievedata from a particular record of the data structure that corresponds tobuilding block 220. The various records of data can be retrieved byanother building block and/or defined for storage using data from anoutput of another building block. In another embodiment, the assignmentmetadata can include a pointer (e.g., a URI, URL) to a network ordatabase location for retrieving data or pushing out data for storage.

In addition, the user can select additional existing building blocks tocascade, combine, or link with an I/O feature (e.g., an output) ofbuilding block 220. In the example illustrated in FIG. 2, the userselected an I/O feature of building block 225 (e.g., an input ofbuilding block 225) to receive an output of building block 220. In thisexample, when the executable logic associated with building block 225 isexecuted at run time, the executable logic, when executed, can analyzethe assignment metadata associated with building block 225 to determinethat an input of building block 225 is to receive an output of buildingblock 220.

In some embodiments, building blocks can retrieve data from records ordatabases and/or push data for storage to records or databases. Forexample, building block 225 can have an I/O feature (e.g., an input)that retrieves data from a database (e.g., database 240). Continuingwith an example above, if open I/O feature A corresponds to a user inputof a user ID, the data representing the user ID can be passed throughbuilding block 220 to an output of building block 220 and into an inputof building block 225. Further, building block 225 can query database240 for additional information associated with the user ID (e.g., usergroups, profile information, etc.). Database 240 can return theadditional information to building block 225, and as an example, theadditional information can be received at an I/O feature (e.g., input)of building block 225.

Further, building blocks can be customized without changing any metadataassociated with the underlying building blocks that are beingcustomized. For example, the user creating new building block 205 canselect building block 230 (e.g., using a menu object discussed later) aspart of building application 200. Building block 230 may have one ormore inputs (e.g., I/O features) and one or more outputs (e.g., I/Ofeature). However, the use may customize the metadata associated withbuilding block 230. For example, if building block 230 includes afunction to display a header with static text, the user can customizebuilding block 230 by adding customized metadata 235. As a furtherexample, customized metadata 235 can include a copy of the metadata ofbuilding block 230, but with a modification to the header to differenttext or to an input received at an I/O feature of building block 225(e.g., the user ID received at building block 220).

It will be appreciated that building blocks 220, 225, and 230 areexisting building blocks that were previously created by a developer.Each of building blocks 220, 225, and 230 can have one or more inputsand one or more outputs. For example, when the user who is creating newbuilding block 205 selects building block 220 from a menu object (e.g.,a dynamically populated drop-down menu), the user interface can displayall of the one or more inputs and one or more outputs previously linkedto building block 220. From this list of one or more inputs and one ormore outputs associated with building block 220, the user can select anI/O feature (e.g., an input and/or an output) from this list to assignto open I/O feature A, for example. The selection of a particular I/Ofeature associated with building block 220 can cause assignment metadata(e.g., metadata identifying the link between open I/O feature A and theselected I/O feature of building block 220) to be created and stored.

In an embodiment, the user can add existing applications to application200. For example, the user can add application 210 and application 215to application 200. In this example, when an existing application isadded to a new application being created, that existing application canbe displayed as a button or link when the new application is rendered ina browser. When the button or link associated with the existingapplication is selected on the displayed new application that isrendered on the browser of a device, the existing application can beexecuted and the functions included in the new application can beperformed.

It will be appreciated that building block data store 245 stores all ofthe existing building blocks and the metadata (e.g., assignmentmetadata) associated with the building blocks. It will also beappreciated that the building block data store 245 can store newbuilding block 205 after it is completed and the assignment metadataidentifying that building blocks 220, 225, and 230 are included in newbuilding block 205, and the links between the building blocks. Forexample, building block data store 245 can store metadata thatidentifies that open I/O feature A of new building block 205 is mappedto a specific I/O feature of building block 220, and so on. It will alsobe appreciated that the menu object included in the user interface candisplay new building block 205 when it is completed (e.g., registered).Advantageously, the menu object is dynamically generated in response toa selection to build a new building block, such that the inputs/outputsare the types of inputs/outputs that are compatible with thecurrent/customized building block, and such that the previously definedbuilding blocks list grows as more building blocks are created.

It will also be appreciated that the building blocks can correspond toweb services (e.g., a REST service). The building block can be called byentering the corresponding URI into a browser. In an embodiment, thecode underlying the building block can be transformed into a webapplication description language (WADL) or web service descriptionlanguage (WSDL). The WADL or WSDL can expose all of the URIs included inthe layout of the building block. A URI can correspond to a container orbuilding block. A user can modify the WADL or WSDL to change the inputparameters that pass through the building block or to change therepresentation of the output (e.g., whether the output is in XML, JSON(JavaScript Object Notation), etc.). In this embodiment, there may notbe a need for an HTML interface because the calling of the web servicecan be achieved by entering the corresponding URI into the browserwindow.

FIG. 3 is a flowchart illustrating a process for building anapplication. Process 300 can be performed to build an application usingone or more existing building blocks that are linkable using metadata.Further, process 300 can be executed at least in part at a user deviceand/or one or more servers. At block 305, an interface configured toenable a user to build an application can be provided. For example, theuser can be a developer that interacts with a user interface executingon a user device to build or create an application. In some instances,the application can be executable on a browser that is running on theuser device (e.g., a mobile device, a smart phone, a tablet computer, alaptop, a desktop, and electronic kiosk, and other suitable devices).Further, building an application on the interface can include linkingbuilding blocks. A building block can correspond to a data structure,and the linking of building blocks defines how data from the datastructure will be processed (e.g., the context for processing datastored in the data structure). For example, linking an output of a firstbuilding block to an input of a second building block defines thecontext of processing the output of the first building block as theinput to the second building block.

At block 310, first input can be received via the interface. Forexample, the first input can correspond to a user requesting to buildinga new building block. In some instances, the first input can correspondto a selection of a button, link, or other selectable object presentedon the interface. In these instances, the selection of the button, link,or other selectable object can initiate the process of defining the newbuilding block (as further described in blocks 315 to 345 below).

At block 315, one or more open I/O features can be added to the newbuilding block. For example, the interface can enable the user to addone or more open I/O features to be assigned to the new building block.In some instances, one or more open I/O features include one or moreopen inputs to the new building block and/or one or more open outputsfrom the new building block. When an open input is added to the newbuilding block, the new building block is configured to receive an input(e.g., a user input received at the interface or an output from anexisting building block). Further, when an open output is added to thenew building block, the new building block is configured to generate anoutput from the new building block.

At block 320, a plurality of existing building blocks can be accessed.Each existing building block of the plurality of existing buildingblocks can correspond to a data structure comprising one or moreexternal I/O features. In some instances, the one or more external I/Ofeatures can include one or more inputs that are defined for storage tothe data structure. Further, in some instances, the one or more externalI/O features can include one or more outputs that are defined forretrieval from the data structure. As discussed below, an external I/Ofeature can be assigned or linked to an open I/O feature of the newbuilding block using the interface.

At block 325, a menu object can be generated and displayed on theinterface. For example, the menu object can facilitate a selection ofone or more building blocks from amongst the plurality of existingbuilding blocks. In some instances, an identifier of some or all of theexisting building blocks can be displayed within the menu object. Forexample, the menu object can be a drop down menu that displays theidentifiers for each of some or all of the existing building blocks.

Advantageously, according to aspects of the present disclosure, when anew building block is created (e.g., generated, built, defined,registered, etc.), that new building block, or at least an identifier ofthat new building block, is included in the one or more existingbuilding blocks that are displayed in the menu object. The menu objectfacilitates selection of one or more existing building blocks in adynamic manner because the menu object displays existing building blocksand new building blocks as they are registered. For example, the menuobject can display a list of existing building blocks, such that eachexisting building block on the list has external I/O features that arecompatible with the open I/O feature of the new building block. The listof existing building blocks displayed within the menu object (inresponse to the selection of the menu object) can be dynamicallyupdated, such that the list of previously-defined building blocks growsas more building blocks are defined. For example, each time a list isrequested for use (e.g., when the menu object is selected) in building anew building block or connecting to an existing building block, the listis generated by determining, at that time, a collection ofthen-available building blocks and/or their I/O features and populatingthe list based on the collection. The new building block, along with themetadata associated with the new building block, may become availablefor selection using the menu object when the new building block isgenerated (e.g., registered, created, built, etc.).

It will also be appreciated that the menu object can display buildingblocks (e.g., or identifiers of building blocks) based on a role of theuser (e.g., the developer). For example, if the user only has limitedpermissions to access a limited set of building blocks, then only thelimited set of building blocks will be displayed when the menu object isselected. However, if the user has full access to all building blocks,then the menu object can display a list of all of the building blocks ora subset of all of the building blocks (e.g., the subset being all ofthe building blocks having compatible I/O features with the selectedopen I/O feature of the new building block).

At block 330, second input corresponding to a selection can be receivedvia the interface. For example, the second input can correspond to aselection of an existing building block from the list of one or moreexisting building blocks displayed in the menu object. In this example,the selection of the existing building block is identified using themenu object (e.g., an item on the list of existing building blocksdisplayed in the menu object is selected). In some instances, uponreceiving the second input, the interface can be modified to display oneor more external I/O features associated with the existing buildingblock that was selected from the menu object. The displayed one or moreexternal I/O features may be available for selection to be linked withan open I/O feature of the new building block.

At block 335, third input corresponding to another selection can bereceived via the interface. For example, the third input can correspondto a selection of a particular external I/O feature of the existingbuilding block selected in the menu object. In some instances, when anexisting building block is selected from a list of building blocksdisplayed in the menu object, the available external I/O features forthat selected building block are also displayed in the interface. Thethird input can correspond to a selection of one of the availableexternal I/O features of the selected building block. The selection of aparticular external I/O feature from a list of available external I/Ofeatures can be linked (e.g., added) to a particular open I/O feature ofthe new building block.

It will be appreciated that, when the available external I/O features ofthe selected existing building block are displayed, a data truncationtest can also be performed. The data truncation test can determine ifthere is potential for data truncation from the mapping of theparticular external I/O feature to the open I/O feature of the newbuilding block. If the potential for data truncation exists, thenvirtual transformation building blocks can be automatically called. Forexample, the virtual transformation building blocks can be automaticallycombined with a selected input (after the input) or output (before theoutput) building block if a selection is made to connect two otherwiseincompatible data types. In this example, the virtual transformationbuilding blocks can be applied in scenarios where data truncation ordata loss can be avoided through data transformation (e.g., int->stringand string(20)->string(40)). In an embodiment, when the virtualtransformation building blocks are called, a message can be presented tothe user on the interface requesting that the user confirm calling ofthe virtual transformation building blocks.

At block 340, the particular external I/O feature (which was selected atblock 335) can be assigned to a particular open I/O feature of the newbuilding block. In some instances, assigning the particular I/O featureto a particular open I/O feature can be achieved by storing assignmentmetadata in association with the new building block. For example, theassignment metadata can include data indicating that the particularexternal I/O feature is linked to the particular open I/O feature of thenew building block. Linking a particular external I/O feature of anexisting building block to a particular open I/O of the new buildingblock can include mapping either an input of the particular buildingblock to an output of the new building block, or an output of theparticular building block to an input of the new building block.

At block 345, a definition of the new building block can be stored. Forexample, the definition of the new building block can include datarepresenting the one or more open I/O features and the assignmentmetadata. In some instances, the assignment metadata can include datathat represents a link to one or more external I/O features of one ormore existing building blocks. Advantageously, when the definition ofthe new building block is stored or registered (e.g., in a data storewithin the building block platform), the new building block can belisted in the menu object as an existing building block if the menuobject is selected at a later time. If a new building block (which hasbeen registered) is selected at a later time using the menu object, thenthe one or more open I/O features can be treated as one or more externalI/O features and displayed in the interface as being available forselection in association with a different new building block.

FIG. 4 is a flowchart illustrating a process for calling building blocksas web services. Process 400 can be performed to call one or morebuilding blocks and/or one or more applications using web services(e.g., a REST service). Further, process 400 can be executed at least inpart at a user device and/or one or more servers. Process 400 begins atblock 405, where a plurality of existing building blocks can beaccessed. In some instances, each existing building block of theplurality of existing building blocks can correspond to a web serviceassociated with a uniform resource identifier (URI). Further, eachexisting building block can correspond to a data structure configured toreceive an input and/or generate an output using executable logic. Insome instances, when the URI associated with the web service is receivedas an input at a web browser, the building block that corresponds to theweb service can be executed. At block 410, a building block from amongstthe plurality of existing building blocks can be identified.

At block 415, the building block (identified at block 410) can betransformed into a machine-readable description language that includesat least one input parameter and a representation of the outputassociated with the building block. For example, the machine-readabledescription language can be a WADL or WSDL transformation of thebuilding block.

At block 420, the web service that corresponds to the building block canbe invoked. In some instances, the invocation of the web service caninclude calling the URI associated with the web service. Further,calling the URI can cause the at least one input parameter to passthrough the building block, such that the output is generated. Forexample, invoking the web service can include receiving the URI of theapplication as an input to a web browser.

At block 425, a communication corresponding to the output of thebuilding block can be received in response to calling the URI associatedwith the web service. For example, the output can be represented inaccordance with the representation of the output included in themachine-readable description language. In some instances, the output canbe stored in the data structure or in another data structure associatedwith the building block. Further, in some instances, the building blockis accessible as a building block that can be combined with otherbuilding blocks within a secure building block architecture service(e.g., such as one that is accessible via authentication) that alsoexposes, for building within the building block architecture service,one or more particular other building blocks that are not exposed usingweb services.

It will be appreciated that an application can be transformed into aREST service (e.g., Web Application Description Language (WADL)). Forexample, the interface can include a wizard that guides the user througha process of transforming the application into the WADL. In thisexample, the user can select an existing application (including one ormore building blocks) or an existing building block using the interface,and then the application (and the one or more building blocks that makeup the application) or the existing building block can be transformedinto the WADL. When the application or the building block is transformedinto the WADL, the WADL can be used to call the application or thebuilding block using one or more URIs included in the WADL. For example,a user outside the building block architecture can view the WADL (e.g.,using an Application Program Interface (API)) and identify the URIs forthe applications or building blocks included in the WADL. Additionally,header properties of the WADL can be modified to define the format ofthe data (e.g., the output of the application or building block) to bereceived in response to calling an application or executing a buildingblock. As a further example, if an application being called using a WADLis configured to output data in HTML, a user can modify a request headerwhen calling the application, such that the output data is received inJSON, instead of HTML.

FIG. 5 is a flowchart illustrating a process for customizingapplications. Process 500 enables a user (e.g., an administrator) toturn on and off customizations that are applied to an application and/orto a building block included in an application. Further, process 500 canbe executed at least in part at a user device and/or one or moreservers. For instance, delivered applications (e.g., applicationsprovided by an application provider, such as PEOPLESOFT™) may becustomized by an administrator. Advantageously, if a deliveredapplication is modified (e.g., with a patch or an update) by theapplication provider, the administrator can turn on or off thecustomizations applied to the delivered application using process 500,for example, in order to determine which modifications were made by theapplication provider.

Process 500 begins at block 505, where an interface is provided to theuser (e.g., displayed on a user device). For example, the interface canbe configured to enable a user to define a customization setting for oneor more building blocks associated with an application. In someinstances, the customization setting for one or more building blocks canbe a setting that indicates whether to apply customized metadata (e.g.,generated by a new application class) to one or more rendering objectsof an existing building block, or to create a custom building block thatgenerates its own rendering object.

At block 510, one or more application classes associated with anapplication can be identified. An application class can be associatedwith one or more rendering objects. For example, a rendering object caninclude executable logic that includes one or more functions configuredto process an input and generate an output. As a further example, anapplication class can be a program including executable code (e.g.,PEOPLECODE™). In some instances, the application class can be identifiedusing the interface (e.g., in event details 910 or 920 as shown in FIG.9). For example, interface 800 can include a tab that links to aninterface page displaying the application classes associated with theapplication or new building block being created.

At block 515, a new application class associated with a new buildingblock can be identified. The new building block can correspond to anexisting building block in that an open I/O feature of the new buildingblock can be linked to an external I/O feature of the existing buildingblock. As an example, the new application class can include newexecutable logic that includes customized metadata. In this example,when an administrator customizes a delivered application, the code forthe customizations can be stored in the new application class. Eachbuilding block can be associated with one or more new rendering objects.For example, when a building block is executed, the data that isgenerated can be stored as an object and passed through a newapplication class, depending on the customization setting. Further, thenew application class can correspond to new executable logic includingcustomized metadata.

At block 520, input can be received via the interface. For example, theinput can include a single click, a single tap, a single swipe, or asingle keypress, or any combination thereof. As another example, theinput can correspond to a selection of a selectable feature (e.g., acheckbox). In some instances, the interface can be a building blockconfiguration interface that facilitates receiving the input. As only anon-limiting illustration, FIGS. 6-9 show examples of interfaces thatmay include a building block configuration interface. In some instances,a state of the selectable feature defines the customization setting forthe new building block. The selection of the selectable feature cancause the state of the selectable feature to be modified (e.g., toggled)between a first mode and a second mode.

At block 525, responsive to the selection (at block 520), the modemetadata can be generated and stored in association with the newbuilding block. For example, the mode metadata can correspond to a firstmode if the state of the selectable feature corresponds to the firstmode, or a second mode if the state of the selectable featurecorresponds to the second mode. The input of block 520 can correspond toa selection (using the selectable feature presented on the interface) ofeither the first mode or the second mode. In some examples, theselection of the second mode using the selectable feature can cause acopy of the one or more rendering objects to be stored in associationwith the new building block (e.g., in a server as metadata). In theseexamples, the new building block is configured, such that at runtime,the new building block generates its own new rendering object and doesnot receive the rendering object of the existing building block asinput.

At block 530, a request can be received to execute the new buildingblock. For example, the request to execute can be a request toinstantiate the new building block. At block 535, in response to therequest received at block 530, it is determined whether the modemetadata corresponds to the first mode or the second mode. For example,if the mode metadata corresponds to the first mode, process 500 proceedsto block 540 where the application class is called, such that thecustomized metadata associated with the new building block is applied tothe one or more rendering objects (e.g., associated with the applicationclass). If the mode metadata is associated with the second mode, process500 proceeds to block 545, where the new application class is called,such that the customized metadata associated with the new building blockis applied the copy of the one or more rendering objects that was storedresponsive to receiving the selection of the selectable feature. In someinstances, the first mode can correspond to a situation in which anexisting building block is customized based on metadata that is executedon top of a (single) rendering object (e.g., customized with metadata).For example, at runtime of executing the new building block, the one ormore rendering objects associated with the application class are passedas input into the new application class and the customized metadata ofthe new application class is executed. The second mode can correspond toa situation in which an existing building block is copied and a custombuilding block is created, such that the custom building block generatesits own rendering object (natively custom), instead of using therendering object of the existing building block. For example, at runtimeof executing the new building block, the one or more rendering objectsassociated with the application class are not passed as input into thenew application class and the one or more new rendering objectsassociated with the new application class are generated.

FIG. 6 shows an example interface for building an application usingexisting building blocks. In an embodiment, the interface can includeLayout Rapid App Designer 600 (referred to herein as app designer 600).For example, app designer 600 can enable a user (e.g., a developer, anadministrator, etc.) to rapidly design, create, or build a newapplication without needing to write any code. In this example, appdesigner 600 enables the user to design a layout (e.g., layout 620) forthe new application that includes one or more existing building blocks(e.g., header 630). The one or more existing building blocks can be tiedtogether or connected using context data (e.g., assignment metadata). Inan embodiment, app designer 600 can include Mobile Application Platform(MAP) Store 610, layout section 620, elements section 640, a “setpermissions” button 650, a “launch application” 660, and a save button670.

MAP Store 610 can include a group search bar and a description bar. Thegroup search bar can enable the user to search for existing buildingblocks to add to layout 620. For example, selecting the group search bar(e.g., the magnifying glass icon) causes a lookup popup window to bepresented to the user. The user can then select a group of one or morebuilding blocks from the lookup popup window. In an embodiment, when abuilding block is selected from the lookup popup window, the buildingblocks included in the group are populated in the “selected groupdescription” section 615. In an embodiment, MAP Store 610 can accessbuilding block data store 245 as shown in FIG. 2. Further, buildingblocks can be customized. When the customized building block iscompleted and stored, that customized building block becomes availablein MAP Store 610 (e.g., becomes available in the lookup popup window),such that the previously defined building blocks list grows as morebuilding blocks are defined.

In some instances, layout 620 can include the core data set that isrendered when the new application is executed. For example, thedeveloper or administrator can select an existing building block thatprompts for an input (e.g., a user ID) that can be populated in the datastructure associated with the selected building block. To achieve this,the developer or administrator would select the building block and addit to layout 620. In some instances, layout 620 indicates what code isrendered and how the code is rendered (e.g., where it is displayed onthe browser screen) when the application is executed (e.g., at runtime). For example, layout 620 can include a header section, a contentsection, and a footer section. The various building blocks can be addedto these different sections of layout 620.

For example, layout 620 can include a building block 630 thatcorresponds to maintenance records. As a non-limiting example, themaintenance records can include records associated with planes, cars, orother suitable vehicle. In this example, building block 630 can includea data structure including values of all of the maintenance recordsassociated with a particular vehicle. Examples of the data structure caninclude a chart, an array, a grid, a table, and excel sheet, and so on.The data structure can include one or more columns of data and one ormore rows of data.

Element section 640 can include one or more elements (e.g., widgets)that can impact properties of the building blocks included in layout620. For example, an element in element section 640 can include a widgetfor changing the representation of the data structure (e.g., to change aview type, change a structure type, change label text, and the like).Using the example of building block 630 being a data structure ofmaintenance records, the properties of building block 630 as it isrepresented in layout 620 can include presenting the maintenance recordsin a table form when the new application is rendered on a browser. Theuser can select building block 630 and also select the widget forchanging the representation of the data structure. Upon selecting thewidget, the properties of building block 630 as it is included in layout620 can be changed (e.g., changing the maintenance records so that theyare represented in a list view as opposed to the table form) when thenew application is rendered using a browser.

In this example, while the representation of the maintenance recordswere changed from a table form to a list view, it will be appreciatedthat the underlying maintenance records (e.g., the values of themaintenance records) were not changed. In this example, the selection ofthe widget only caused the table form of the maintenance records to betransformed into a list view of the maintenance records. According toembodiments of the present disclosure, the layout (e.g., layout section620) changes the representation and properties of the building blocksthat are included in the new application, such that the building blocksare presented in accordance with the determined properties. In anembodiment, a modification to the representation and properties of abuilding block when the building block is included in layout 620 refersto a modification of the metadata of the building block only withinlayout 620. In this embodiment, the modifications to the metadata of thebuilding block within layout 620 (e.g., modifying building block 630 sothat the data structure is represented as a list view instead of a tableform at run time) do not impact the metadata of the underlying buildingblock (e.g., as stored in building block data store 245, or asaccessible by the MAP Store, etc.). For example, the underlying buildingblock still corresponds to the data structure (e.g., the records thatstore the maintenance records of the vehicle are unchanged), but onlythe representation (e.g., table form or list view) is changed whenbuilding block 630 is added to layout 620.

App designer 600 can also include a “set permissions” button 650, a“launch application” button 660, and a “save” button 670. In an example,the “set permissions” button 650 can be selected to define thepermissions associated with each building block and/or application. Forexample, permissions can be set to require that valid login credentialsbefore the functionality of a building block can be accessed by an enduser of the application. In another embodiment, end users of theapplication can have full access to a subset of building blocks, and canhave limited access (e.g., requiring login credentials) for anothersubset of building blocks. Further, the “launch application” button 660can launch the new application. For example, launching the applicationcan render the building blocks in layout 620 on a browser window.Further, the “save” button 670 can be clicked to save the current status(e.g., current configuration or properties) of the building blocks inlayout 620.

It will be appreciated that a building block can include definitions ofcontexts (e.g., the building block, when called, prompts the end user ofthe application to enter a mailing address). When the building block isincluded in the new application, the building block can includedifferent URIs that the developer used when the building block wascreated. When certain input is inputted into the building block, theoutput can be determined. For example, the user can tie the output of anexisting building block and feed that into an input of a new buildingblock being created for a new application.

FIG. 7 an example interface for mapping primitives to data structures ofbuilding blocks. The interface can include URI Mapping page 700. When abuilding block is selected from the Selected Group Description 615 (asshown in FIG. 6), the URI Mapping page 700 can be displayed. The URIMapping page 700 enables a user to add an open I/O feature (e.g., anunassigned input) to the selected building block using metadata from theexisting building block (e.g., assignment metadata that identifies anyother I/O features of other building blocks mapped to an I/O feature ofthe existing building block). In an embodiment, URI Mapping page 700 caninclude a “mapping layouts” menu object 710, “available layout URIs”section 720, “URI elements requiring mapping” section 730, and“available primitives” section 740. For example, a primitive can be adata element included in a data structure.

In an embodiment, assignment metadata can correspond to the mappinginformation of I/O features defined for a particular building block. Ifa user (e.g., a developer) builds an application using app designer 600,for example, the user can define what location to get inputs (e.g., arecord location in a data structure) and what location to store outputs(e.g., a record location in a data structure) for a new building blockto be rendered when the application is called (e.g., executed). At theapplication layer of the new application or building block, for example,there may be a Representational State Transfer (REST) service that iscreated. The REST service can identify the URI that corresponds to theinput, for example. The specific context of data can be based off theURI. When the user builds an application, the user actually is buildingthe URI because when the user defines the application, and the user canadd the one or more inputs, which can return specific context when theapplication is rendered at run time (e.g., using a browser). Further,the output that is received after the application is rendered cancorrespond to the logical structure of data that is used to drive theapplication. For example, the building block data store 245 can provideaccess to a plurality of existing building blocks. As described above, abuilding block is a piece of code of an existing application. When a newbuilding block is being created, the open I/O features of the newbuilding block can be added or defined. The open I/O features for thenew building block can be the inputs for that building block, fromanother building block, or from the user interface. These inputs can bepassed through the application, which would generate contextual datathat that application uses, and the user can take that data and map thatto an input of another building block.

In the example URI Mapping page 700 of FIG. 7, when a building block isselected to be added to the new application (as shown with respect toFIG. 6), the URI Mapping page 700 can be presented to the user to enablethe user to add open I/O features to the new building block, and to mapthe open I/O features to I/O features of existing building blocks. Forexample, the “mapping layouts” menu object 710 provides a drop-down menushowing all of the I/O features that exists for an added open I/Ofeature of the new building block that is added to the new application.For example, “available layout URIs” section 720 shows a list of definedopen I/O features for the new building block. In this example, the openI/O features for the new building block include “A/C Number,” “PilotName,” and “Fight Test Destination.” As a further example, the user canselect at least one of the items (e.g., “Pilot Name”) in “availablelayout URIs” section 720 as an open input of the new building block.Accordingly, the inputs can be of a particular data type (e.g.,string(30)) given that that the selected open input of the new buildingblock is, for example, “Pilot Name” as shown by the selected checkboxcorresponding to “Pilot Name.”

The “mapping layouts” menu object 710 provides a drop-down menu of allavailable contextual building blocks from which the open input can betaken. For example, “mapping layouts” menu object 710 can display adrop-down menu object of all existing building blocks from which datarepresenting the “Pilot Name” can be taken. In FIG. 7, “mapping layouts”menu object shows that the “Pilot Name” (selected in the “availablelayout URIs” section 720) can be taken from the building block thatcorresponds to “Maintenance Records.” Further, examples of the menuobject of “mapping layouts” menu object 710 can include a drop downlist, a search field with predictive text, a flyout menu, a droplinemenu, an accordion menu, or other suitable menu object.

In some embodiments, a data type checking analysis is performed, suchthat the building blocks listed in the drop-down menu of “mappinglayouts” menu object 710 all correspond to the same data type as theselected open input (e.g., “Pilot Name”), which was selected in“available layout URIs” section 720. For example, the data type ofstring(30) can be retrieved from the building block associated withmaintenance records and can be fed into the open I/O feature of “PilotName,” which also has a data type of string(30).

In some embodiments, “available primitives” section 740 can show allprimitives in the data structure that correspond to the maintenancerecords building block. For example, a primitive can be a data elementincluded in the data structure. In this example, the maintenance recordsbuilding block corresponds to a data structure that includes primitives(e.g., records) of “pilot,” “aircraft number,” “squadron,” “aircrafttype,” and so on. In some embodiments, the primitives shown in“available primitives” section 740 can be primitives that share acompatible data type as the selected open I/O feature “Pilot Name”(e.g., only primitives that share a string(30) data type with the openI/O feature).

In one embodiment, if a primitive having a data type of an integer isselected to be mapped with the open I/O feature that has a data type ofstring(30), the URI Mapping page 700 can present an error indicatingthat the mapping is incompatible. For example, an incompatible mappingcan refer to the potential occurrence of data truncation if an I/Ofeature were fed into the selected open I/O feature of the new buildingblock. In another embodiment, a data truncation test can be performedupon the selection of an available primitive for mapping onto the openI/O feature. For example, the data truncation test can determine if thedata can be mapped from the selected primitive (e.g., “pilot” 750) tothe open I/O feature (e.g., “Pilot Name”) without data truncation.

If the potential for data truncation exists from the mapping, thenvirtual transformation building blocks can be automatically called. Forexample, the virtual transformation building blocks can be automaticallycombined with a selected input (after the input) or output (before theoutput) building block if a selection is made to connect two otherwiseincompatible data types. In this example, the virtual transformationbuilding blocks can be applied in scenarios where data truncation ordata loss can be avoided through data transformation (e.g., int->stringand string(20)->string(40)). In an embodiment, when the virtualtransformation building blocks are called, a message can be presented tothe user requesting that the calling of the virtual transformationbuilding blocks be confirmed by the user before the transformationbuilding blocks are called.

In an embodiment, the selection of a primitive from the “availableprimitives” section 740 can be performed by receiving an inputcorresponding to a selection of the checkbox next to “Primitive” in the“URI Elements Requiring Mapping” section 730. Upon checking the checkboxnext to “Primitive” in the “URI Elements Requiring Mapping” section 730,the URI Mapping page 700 presents a page to the user where the user canselect an available primitive from the list of available primitives. Inone embodiment, the page also shows the various data types associatedwith the available primitives, such that if the user selects a primitivehaving an incompatible data type, then a warning or error message can bedisplayed. In another embodiment, the virtual transformation buildingblocks can be automatically called to facilitate a transformation of themapped data, such that data truncation does not occur. Further,selection of “Constant” in the “URI elements requiring mapping” section730 can prompt the user to enter text that can be used as static text,such that the input of “Pilot Name” may always be the entered text.

It will be appreciated that the “mapping layouts” menu object 710, whenselected, can display a hierarchy of available building blocks to whichthe open I/O feature can be mapped. It will also be appreciated that thebuilding blocks can be categorized manually, automatically, or by theowner of the building block (e.g., the developer who created thebuilding block). The categorization of the building blocks can be usedto sort the list of displayed building blocks available for mapping. Itwill also be appreciated that the “mapping layouts” menu object 710 canalso be a search tab that populates the relevant building blocks as textis entered into the search tab (e.g., using predictive text techniques).It will also be appreciated that menu object 710 can display buildingblocks based on a role of the user (e.g., the developer). For example,if the user only has limited permissions to access a limited set ofbuilding blocks, then only the limited set of building blocks will bedisplayed when the menu object 710 is selected. However, if the user hasfull access to all building blocks, then the menu object can display alist of all of the building blocks or a subset of all of the buildingblocks (e.g., the subset being all of the building blocks havingcompatible I/O features with the selected open I/O feature of the newbuilding block).

FIG. 8 shows an example interface for building an application usingcontainers. FIG. 6 showed an example interface for building anapplication using a rapid app designer 600, where the user did not needto write any code. However, FIG. 8 shows an example interface forbuilding an application using containers (e.g., used interchangeablywith building blocks herein), such that the user may need to write codeto customize the containers and/or events associated with thecontainers. The example interface of FIG. 8 is an application designerinterface 800 that includes layout 810, parent data structure 840, andcustom data structure 850. In some embodiments, application designerinterface 800 enables a user to define data structures and to customizeexisting containers and data structures. Further, application designerinterface 800 also enables a user (e.g., a developer) to define inputsfor containers and data structures associated with the containers. Forexample, a user can define that a container will receive an input of auser ID, then the user can select a user id primitive (e.g., dataelement) from parent data structure 840 or custom data structure 850.

In an embodiment, a containers (e.g., container 820) can refer tobuilding blocks. For example, a container can refer to a section on apage (e.g., a header, content section, a footer, etc.). Further, thecontext metadata (e.g., the assignment metadata) can be the mapping ofcontainers to one or more other containers, such that the I/O featuresof one container are the types of I/O features that are compatible withthe other containers. For example, one container can show a list offlight cards. For one application, whenever code is wrapped in acontainer, that container is defined in a building block data store.While an application can include one or more containers, on the back end(e.g., the servers rendering the code) the complete application is beingexecuted.

Layout 810 can include one or more containers that will make up theapplication being built by the user. For example, a container can be aheader of the application when the application is rendered on a browser.In this example, the user can add existing containers frompreviously-built applications, customize the existing containers, orcreate new containers. When a container is added to layout 810, the usercan associate a primitive (e.g., a data element of a data structure)with the container, such that the defined inputs can populate the rowsand columns of the data structure. In an embodiment, the data structurecan drive the data used in the application. For example, if thecontainer corresponds to an input (e.g., code that gets a value orinput), then a data element (e.g., primitive) of the data structure canbe mapped to the container such that the input of the container comesfrom the data element.

For example, layout 810 can include container 820 corresponding to“Mapbutton_2,” which can be a button displayed on a browser page whenthe application is executed. The “Label Text” column can be modified bythe user, such that the text entered in the “Label Text” box can bepresented on the browser page when the application is executed. Further,properties 830 can be a link to another page or a popup window ofapplication designer 800 that enables the user to customize metadataassociated with container 820. For example, the user can map container820 to a primitive of data structure 840 or custom data structure 850.

In an embodiment, parent data structure 840 can be customized by theuser. For example, to customize the EXAMPLE Application, the user cancreate a new Layout via the MAP Layout Designer as Type: custom andassign layout 810 to be customized (Parent Layout). The user has theoption to assign an additional data structure (e.g., custom datastructure 850) to the customized layout (which is different from layout810). Application designer 800 can display both the data structure 840(e.g., corresponding to layout 810, the Parent Layout) and custom datastructure 850 (e.g., corresponding to at least a portion of datastructure 840) on the left side. For the custom layout (not shown), thepage is initially empty of elements other than the Header and Footercontainers. The application designer 800 can display all the eventsassigned to a container included in layout 810. Further, the user canoptionally assign their own created application classes that can be usedto modify any data and content assigned on the layout 810.

FIG. 9 shows an example interface for customizing metadata associatedwith the containers shown in FIG. 8. The example interface can includebuilding block configuration interface 900. Building block configurationinterface 900 can include event details 910 and 930 for the parentapplication (e.g., the original application that is potentially beingcustomized). The event details describe the configuration settings forevents. For example, the parent application can include a save button,such that when the save button is clicked a save event occurs (e.g., apopup window appears on the browser with a message). Further, buildingblock configuration interface 900 can also include custom event details920 and 940. The custom event details can include customizations made tocontainers of the parent application that are included in the customapplication. For example, the user can add a custom application byadding containers from the parent application to a custom layout. Anychanges or customizations made to the containers added to the customlayout would not affect the metadata of the containers included in theparent application because these containers are added to the new customlayout and their corresponding metadata is also saved in associationwith the custom layout. Accordingly, in some embodiments, changes madeto the containers in the custom layout impact the container in thecustom application, but not the same container in the parentapplication.

For example, the assigned application class for “Event Type: INIT” canmodify the corresponding container of the parent application, such thatthe value entered for the “Entry Input Element” reads “Custom Input”.Further, the assigned application class for “Event Type: SAVE” canmodify the corresponding container of the parent application, such thatthe popup text will display “Data Submit read from Custom Example.” Inan embodiment, at runtime, the MAP framework builds (e.g., merges) theparent application metadata (e.g., from the EXAMPLE application) withthat of the custom metadata of the custom application to generate thecustomized application. Additionally, the original EXAMPLE metadata isnot affected such that if the project with the EXAMPLE metadata wasre-imported it would have no effect to the customized metadata. The user(e.g., a developer) can add additional pages to the EXAMPLE applicationby adding pages via the customized layout. If the user wants to run theoriginal parent application (e.g., the EXAMPLE application), the usercan turn off the Custom changes by selecting the “No Custom” check boxon the custom layout. For example, the user can via People Code based oncontext at runtime selectively decide in a piecemeal manner whichcontainer element(s) to use from either the original application(EXAMPLE) or the custom application.

As another example, the user has the option of calling the applicationclass for the event of the parent application and running the customizedevent on top of running the parent event, or calling the customizedapplication class with the customized event only. In this example, theuser can unselect checkbox 950, if the user wants to call theapplication class for the event of the parent application and runningthe customized event on top of running the parent event. Further, theuser can select checkbox 950, if the user wants to call the customizedapplication class with the customized event only. In this latterexample, no rendering objects of the parent application will be renderedat runtime, instead, only the rendering objects in the application classof the customized event will be rendered at runtime. For example, if theparent has business logic that the user would like to use in thecustomized events, the user can unselect checkbox 950. In this example,the parent application still runs, but once the parent runs, the parentevent (e.g., the save event), the data structure associated with thecontainer of the parent event is populated and included in the renderingobject of the parent event. Before the rendering object renders, theuser can modify the MAP object (e.g., change data, remove rows, changeproperty values, etc.). In this case, the parent application's renderingobject will be rendered at runtime, but with the values of thecustomized portions (e.g., with the custom event details 920). Inanother embodiment, the user can select checkbox 950 (“Custom eventonly”), so that the rendering object of the parent application is notrendered, but rather, only the application class of the customized eventwill be rendered at run time. For example, only the custom event wouldrun, and not run the parent logic. It will be appreciated that thecustomizations are autonomous to the parent because the original parentmetadata is unmodified when the parent event is modified in a customizedapplication. Advantageously, upgrades or patches made to the parentapplication do not impact the customized application. As anotheradvantage, the checkbox 950 is available for each container included inthe customized application. For example, for each container in thecustom application, the user can selectively run the custom event or theparent event. Further, when running the parent event with the customizedmetadata, the rendering object of the parent application can be changedto accomplish customization, and the parent application runs as is withthe customized metadata. It will be appreciated that the customizedmetadata can be overridden on a container-by-container basis. Forexample, using the properties (e.g., properties link 830 of FIG. 8), thecustomized metadata of a container can be overridden, such that even ofthe associated checkbox 950 for the container is selected, thecustomized metadata would not be rendered at runtime, but rather theparent container building block would run. The ability to overridecustomized metadata in the properties section of the containers can beperformed on a piecemeal basis (e.g., on a container-by-containerbasis).

FIG. 10 depicts a simplified diagram of a distributed system 1000 forimplementing one of the embodiments. In the illustrated embodiment,distributed system 1000 includes one or more client computing devices1002, 1004, 1006, and 1008, which are configured to execute and operatea client application such as a web browser, proprietary client (e.g.,Oracle Forms), or the like over one or more network(s) 1010. Server 1012may be communicatively coupled with remote client computing devices1002, 1004, 1006, and 1008 via network 1010.

In various embodiments, server 1012 may be adapted to run one or moreservices or software applications provided by one or more of thecomponents of the system. In some embodiments, these services may beoffered as web-based or cloud services or under a Software as a Service(SaaS) model to the users of client computing devices 1002, 1004, 1006,and/or 708. Users operating client computing devices 1002, 1004, 1006,and/or 1008 may in turn utilize one or more client applications tointeract with server 1012 to utilize the services provided by thesecomponents.

In the configuration depicted in the figure, the software components1018, 1020 and 1022 of system 1000 are shown as being implemented onserver 1012. In other embodiments, one or more of the components ofsystem 1000 and/or the services provided by these components may also beimplemented by one or more of the client computing devices 1002, 1004,1006, and/or 1008. Users operating the client computing devices may thenutilize one or more client applications to use the services provided bythese components. These components may be implemented in hardware,firmware, software, or combinations thereof. It should be appreciatedthat various different system configurations are possible, which may bedifferent from distributed system 1000. The embodiment shown in thefigure is thus one example of a distributed system for implementing anembodiment system and is not intended to be limiting.

Client computing devices 1002, 1004, 1006, and/or 1008 may be portablehandheld devices (e.g., an iPhone®, cellular telephone, an iPad®,computing tablet, a personal digital assistant (PDA)) or wearabledevices (e.g., a Google Glass® head mounted display), running softwaresuch as Microsoft Windows Mobile®, and/or a variety of mobile operatingsystems such as iOS, Windows Phone, Android, BlackBerry 10, Palm OS, andthe like, and being Internet, e-mail, short message service (SMS),Blackberry®, or other communication protocol enabled. The clientcomputing devices can be general purpose personal computers including,by way of example, personal computers and/or laptop computers runningvarious versions of Microsoft Windows®, Apple Macintosh®, and/or Linuxoperating systems. The client computing devices can be workstationcomputers running any of a variety of commercially-available UNIX® orUNIX-like operating systems, including without limitation the variety ofGNU/Linux operating systems, such as for example, Google Chrome OS.Alternatively, or in addition, client computing devices 1002, 1004,1006, and 1008 may be any other electronic device, such as a thin-clientcomputer, an Internet-enabled gaming system (e.g., a Microsoft Xboxgaming console with or without a Kinect® gesture input device), and/or apersonal messaging device, capable of communicating over network(s) 710.

Although exemplary distributed system 1000 is shown with four clientcomputing devices, any number of client computing devices may besupported. Other devices, such as devices with sensors, etc., mayinteract with server 1012.

Network(s) 1010 in distributed system 1000 may be any type of networkfamiliar to those skilled in the art that can support datacommunications using any of a variety of commercially-availableprotocols, including without limitation TCP/IP (transmission controlprotocol/Internet protocol), SNA (systems network architecture), IPX(Internet packet exchange), AppleTalk, and the like. Merely by way ofexample, network(s) 1010 can be a local area network (LAN), such as onebased on Ethernet, Token-Ring and/or the like. Network(s) 1010 can be awide-area network and the Internet. It can include a virtual network,including without limitation a virtual private network (VPN), anintranet, an extranet, a public switched telephone network (PSTN), aninfra-red network, a wireless network (e.g., a network operating underany of the Institute of Electrical and Electronics (IEEE) 802.11 suiteof protocols, Bluetooth®, and/or any other wireless protocol); and/orany combination of these and/or other networks.

Server 1012 may be composed of one or more general purpose computers,specialized server computers (including, by way of example, PC (personalcomputer) servers, UNIX® servers, mid-range servers, mainframecomputers, rack-mounted servers, etc.), server farms, server clusters,or any other appropriate arrangement and/or combination. In variousembodiments, server 1012 may be adapted to run one or more services orsoftware applications described in the foregoing disclosure. Forexample, server 1012 may correspond to a server for performingprocessing described above according to an embodiment of the presentdisclosure.

Server 1012 may run an operating system including any of those discussedabove, as well as any commercially available server operating system.Server 1012 may also run any of a variety of additional serverapplications and/or mid-tier applications, including HTTP (hypertexttransport protocol) servers, FTP (file transfer protocol) servers, CGI(common gateway interface) servers, JAVA® servers, database servers, andthe like. Exemplary database servers include without limitation thosecommercially available from Oracle, Microsoft, Sybase, IBM(International Business Machines), and the like.

In some implementations, server 1012 may include one or moreapplications to analyze and consolidate data feeds and/or event updatesreceived from users of client computing devices 1002, 1004, 1006, and1008. As an example, data feeds and/or event updates may include, butare not limited to, Twitter® feeds, Facebook® updates or real-timeupdates received from one or more third party information sources andcontinuous data streams, which may include real-time events related tosensor data applications, financial tickers, network performancemeasuring tools (e.g., network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like. Server 1012 may also include one or moreapplications to display the data feeds and/or real-time events via oneor more display devices of client computing devices 1002, 1004, 1006,and 1008.

Distributed system 1000 may also include one or more databases 1014 and1016. Databases 1014 and 1016 may reside in a variety of locations. Byway of example, one or more of databases 1014 and 1016 may reside on anon-transitory storage medium local to (and/or resident in) server 1012.Alternatively, databases 1014 and 1016 may be remote from server 1012and in communication with server 1012 via a network-based or dedicatedconnection. In one set of embodiments, databases 1014 and 1016 mayreside in a storage-area network (SAN). Similarly, any necessary filesfor performing the functions attributed to server 1012 may be storedlocally on server 1012 and/or remotely, as appropriate. In one set ofembodiments, databases 1014 and 1016 may include relational databases,such as databases provided by Oracle, that are adapted to store, update,and retrieve data in response to SQL-formatted commands.

FIG. 11 is a simplified block diagram of one or more components of asystem environment 1100 by which services provided by one or morecomponents of an embodiment system may be offered as cloud services, inaccordance with an embodiment of the present disclosure. In theillustrated embodiment, system environment 1100 includes one or moreclient computing devices 1104, 1106, and 1108 that may be used by usersto interact with a cloud infrastructure system 1102 that provides cloudservices. The client computing devices may be configured to operate aclient application such as a web browser, a proprietary clientapplication (e.g., Oracle Forms), or some other application, which maybe used by a user of the client computing device to interact with cloudinfrastructure system 1102 to use services provided by cloudinfrastructure system 1102.

It should be appreciated that cloud infrastructure system 1102 depictedin the figure may have other components than those depicted. Further,the embodiment shown in the figure is only one example of a cloudinfrastructure system that may incorporate an embodiment of theinvention. In some other embodiments, cloud infrastructure system 1102may have more or fewer components than shown in the figure, may combinetwo or more components, or may have a different configuration orarrangement of components.

Client computing devices 1104, 1106, and 1108 may be devices similar tothose described above for 1002, 1004, 1006, and 1008.

Although exemplary system environment 1100 is shown with three clientcomputing devices, any number of client computing devices may besupported. Other devices such as devices with sensors, etc. may interactwith cloud infrastructure system 1102.

Network(s) 1110 may facilitate communications and exchange of databetween clients 1104, 1106, and 1108 and cloud infrastructure system1102. Each network may be any type of network familiar to those skilledin the art that can support data communications using any of a varietyof commercially-available protocols, including those described above fornetwork(s) 1110.

Cloud infrastructure system 1102 may comprise one or more computersand/or servers that may include those described above for server 1012.

In certain embodiments, services provided by the cloud infrastructuresystem may include a host of services that are made available to usersof the cloud infrastructure system on demand, such as online datastorage and backup solutions, Web-based e-mail services, hosted officesuites and document collaboration services, database processing, managedtechnical support services, and the like. Services provided by the cloudinfrastructure system can dynamically scale to meet the needs of itsusers. A specific instantiation of a service provided by cloudinfrastructure system is referred to herein as a “service instance.” Ingeneral, any service made available to a user via a communicationnetwork, such as the Internet, from a cloud service provider's system isreferred to as a “cloud service.” Typically, in a public cloudenvironment, servers and systems that make up the cloud serviceprovider's system are different from the customer's own on-premisesservers and systems. For example, a cloud service provider's system mayhost an application, and a user may, via a communication network such asthe Internet, on demand, order and use the application.

In some examples, a service in a computer network cloud infrastructuremay include protected computer network access to storage, a hosteddatabase, a hosted web server, a software application, or other serviceprovided by a cloud vendor to a user, or as otherwise known in the art.For example, a service can include password-protected access to remotestorage on the cloud through the Internet. As another example, a servicecan include a web service-based hosted relational database and ascript-language middleware engine for private use by a networkeddeveloper. As another example, a service can include access to an emailsoftware application hosted on a cloud vendor's web site.

In certain embodiments, cloud infrastructure system 1102 may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such a cloud infrastructure system is the Oracle Public Cloudprovided by the present assignee.

In various embodiments, cloud infrastructure system 1102 may be adaptedto automatically provision, manage and track a customer's subscriptionto services offered by cloud infrastructure system 1102. Cloudinfrastructure system 1102 may provide the cloud services via differentdeployment models. For example, services may be provided under a publiccloud model in which cloud infrastructure system 1102 is owned by anorganization selling cloud services (e.g., owned by Oracle) and theservices are made available to the general public or different industryenterprises. As another example, services may be provided under aprivate cloud model in which cloud infrastructure system 1102 isoperated solely for a single organization and may provide services forone or more entities within the organization. The cloud services mayalso be provided under a community cloud model in which cloudinfrastructure system 1102 and the services provided by cloudinfrastructure system 1102 are shared by several organizations in arelated community. The cloud services may also be provided under ahybrid cloud model, which is a combination of two or more differentmodels.

In some embodiments, the services provided by cloud infrastructuresystem 802 may include one or more services provided under Software as aService (SaaS) category, Platform as a Service (PaaS) category,Infrastructure as a Service (IaaS) category, or other categories ofservices including hybrid services. A customer, via a subscriptionorder, may order one or more services provided by cloud infrastructuresystem 1102. Cloud infrastructure system 1102 then performs processingto provide the services in the customer's subscription order.

In some embodiments, the services provided by cloud infrastructuresystem 802 may include, without limitation, application services,platform services and infrastructure services. In some examples,application services may be provided by the cloud infrastructure systemvia a SaaS platform. The SaaS platform may be configured to providecloud services that fall under the SaaS category. For example, the SaaSplatform may provide capabilities to build and deliver a suite ofon-demand applications on an integrated development and deploymentplatform. The SaaS platform may manage and control the underlyingsoftware and infrastructure for providing the SaaS services. Byutilizing the services provided by the SaaS platform, customers canutilize applications executing on the cloud infrastructure system.Customers can acquire the application services without the need forcustomers to purchase separate licenses and support. Various differentSaaS services may be provided. Examples include, without limitation,services that provide solutions for sales performance management,enterprise integration, and business flexibility for largeorganizations.

In some embodiments, platform services may be provided by the cloudinfrastructure system via a PaaS platform. The PaaS platform may beconfigured to provide cloud services that fall under the PaaS category.Examples of platform services may include without limitation servicesthat enable organizations (such as Oracle) to consolidate existingapplications on a shared, common architecture, as well as the ability tobuild new applications that leverage the shared services provided by theplatform. The PaaS platform may manage and control the underlyingsoftware and infrastructure for providing the PaaS services. Customerscan acquire the PaaS services provided by the cloud infrastructuresystem without the need for customers to purchase separate licenses andsupport. Examples of platform services include, without limitation,Oracle Java Cloud Service (JCS), Oracle Database Cloud Service (DBCS),and others.

By utilizing the services provided by the PaaS platform, customers canemploy programming languages and tools supported by the cloudinfrastructure system and also control the deployed services. In someembodiments, platform services provided by the cloud infrastructuresystem may include database cloud services, middleware cloud services(e.g., Oracle Fusion Middleware services), and Java cloud services. Inone embodiment, database cloud services may support shared servicedeployment models that enable organizations to pool database resourcesand offer customers a Database as a Service in the form of a databasecloud. Middleware cloud services may provide a platform for customers todevelop and deploy various business applications, and Java cloudservices may provide a platform for customers to deploy Javaapplications, in the cloud infrastructure system.

Various different infrastructure services may be provided by an IaaSplatform in the cloud infrastructure system. The infrastructure servicesfacilitate the management and control of the underlying computingresources, such as storage, networks, and other fundamental computingresources for customers utilizing services provided by the SaaS platformand the PaaS platform.

In certain embodiments, cloud infrastructure system 1102 may alsoinclude infrastructure resources 1130 for providing the resources usedto provide various services to customers of the cloud infrastructuresystem. In one embodiment, infrastructure resources 1130 may includepre-integrated and optimized combinations of hardware, such as servers,storage, and networking resources to execute the services provided bythe PaaS platform and the SaaS platform.

In some embodiments, resources in cloud infrastructure system 802 may beshared by multiple users and dynamically re-allocated per demand.Additionally, resources may be allocated to users in different timezones. For example, cloud infrastructure system 1130 may enable a firstset of users in a first time zone to utilize resources of the cloudinfrastructure system for a specified number of hours and then enablethe re-allocation of the same resources to another set of users locatedin a different time zone, thereby maximizing the utilization ofresources.

In certain embodiments, a number of internal shared services 1132 may beprovided that are shared by different components or modules of cloudinfrastructure system 1102 and by the services provided by cloudinfrastructure system 1102. These internal shared services may include,without limitation, a security and identity service, an integrationservice, an enterprise repository service, an enterprise managerservice, a virus scanning and white list service, a high availability,backup and recovery service, service for enabling cloud support, anemail service, a notification service, a file transfer service, and thelike.

In certain embodiments, cloud infrastructure system 802 may providecomprehensive management of cloud services (e.g., SaaS, PaaS, and IaaSservices) in the cloud infrastructure system. In one embodiment, cloudmanagement functionality may include capabilities for provisioning,managing and tracking a customer's subscription received by cloudinfrastructure system 1102, and the like.

In one embodiment, as depicted in the figure, cloud managementfunctionality may be provided by one or more modules, such as an ordermanagement module 1120, an order orchestration module 1122, an orderprovisioning module 1124, an order management and monitoring module1126, and an identity management module 1128. These modules may includeor be provided using one or more computers and/or servers, which may begeneral purpose computers, specialized server computers, server farms,server clusters, or any other appropriate arrangement and/orcombination.

In exemplary operation 1134, a customer using a client device, such asclient device 1104, 1106 or 1108, may interact with cloud infrastructuresystem 1102 by requesting one or more services provided by cloudinfrastructure system 1102 and placing an order for a subscription forone or more services offered by cloud infrastructure system 1102. Incertain embodiments, the customer may access a cloud User Interface(UI), cloud UI 1112, cloud UI 1114 and/or cloud UI 1116 and place asubscription order via these UIs. The order information received bycloud infrastructure system 1102 in response to the customer placing anorder may include information identifying the customer and one or moreservices offered by the cloud infrastructure system 1102 that thecustomer intends to subscribe to.

After an order has been placed by the customer, the order information isreceived via the cloud UIs, 1112, 1114 and/or 1116.

At operation 1136, the order is stored in order database 1118. Orderdatabase 1118 can be one of several databases operated by cloudinfrastructure system 1118 and operated in conjunction with other systemelements.

At operation 1138, the order information is forwarded to an ordermanagement module 1120. In some instances, order management module 1120may be configured to perform billing and accounting functions related tothe order, such as verifying the order, and upon verification, bookingthe order.

At operation 1140, information regarding the order is communicated to anorder orchestration module 1122. Order orchestration module 1122 mayutilize the order information to orchestrate the provisioning ofservices and resources for the order placed by the customer. In someinstances, order orchestration module 1122 may orchestrate theprovisioning of resources to support the subscribed services using theservices of order provisioning module 1124.

In certain embodiments, order orchestration module 1122 enables themanagement of business processes associated with each order and appliesbusiness logic to determine whether an order should proceed toprovisioning. At operation 1142, upon receiving an order for a newsubscription, order orchestration module 1122 sends a request to orderprovisioning module 1124 to allocate resources and configure thoseresources needed to fulfill the subscription order. Order provisioningmodule 1124 enables the allocation of resources for the services orderedby the customer. Order provisioning module 1124 provides a level ofabstraction between the cloud services provided by cloud infrastructuresystem 1100 and the physical implementation layer that is used toprovision the resources for providing the requested services. Orderorchestration module 1122 may thus be isolated from implementationdetails, such as whether or not services and resources are actuallyprovisioned on the fly or pre-provisioned and only allocated/assignedupon request.

At operation 1144, once the services and resources are provisioned, anotification of the provided service may be sent to customers on clientdevices 1104, 1106 and/or 1108 by order provisioning module 1124 ofcloud infrastructure system 1102.

At operation 1146, the customer's subscription order may be managed andtracked by an order management and monitoring module 1126. In someinstances, order management and monitoring module 1126 may be configuredto collect usage statistics for the services in the subscription order,such as the amount of storage used, the amount data transferred, thenumber of users, and the amount of system up time and system down time.

In certain embodiments, cloud infrastructure system 1100 may include anidentity management module 1128. Identity management module 1128 may beconfigured to provide identity services, such as access management andauthorization services in cloud infrastructure system 1100. In someembodiments, identity management module 1128 may control informationabout customers who wish to utilize the services provided by cloudinfrastructure system 1102. Such information can include informationthat authenticates the identities of such customers and information thatdescribes which actions those customers are authorized to performrelative to various system resources (e.g., files, directories,applications, communication ports, memory segments, etc.) Identitymanagement module 1128 may also include the management of descriptiveinformation about each customer and about how and by whom thatdescriptive information can be accessed and modified.

FIG. 12 illustrates an exemplary computer system 1200, in which variousembodiments of the present invention may be implemented. The system 1200may be used to implement any of the computer systems described above. Asshown in the figure, computer system 1200 includes a processing unit1204 that communicates with a number of peripheral subsystems via a bussubsystem 1202. These peripheral subsystems may include a processingacceleration unit 1206, an I/O subsystem 1208, a storage subsystem 1218and a communications subsystem 1224. Storage subsystem 1218 includestangible computer-readable storage media 1222 and a system memory 1210.

Bus subsystem 1202 provides a mechanism for letting the variouscomponents and subsystems of computer system 1200 communicate with eachother as intended. Although bus subsystem 1202 is shown schematically asa single bus, alternative embodiments of the bus subsystem may utilizemultiple buses. Bus subsystem 1202 may be any of several types of busstructures including a memory bus or memory controller, a peripheralbus, and a local bus using any of a variety of bus architectures. Forexample, such architectures may include an Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnect (PCI) bus, which can beimplemented as a Mezzanine bus manufactured to the IEEE P1386.1standard.

Processing unit 1204, which can be implemented as one or more integratedcircuits (e.g., a conventional microprocessor or microcontroller),controls the operation of computer system 1200. One or more processorsmay be included in processing unit 1204. These processors may includesingle core or multicore processors. In certain embodiments, processingunit 1204 may be implemented as one or more independent processing units1232 and/or 1234 with single or multicore processors included in eachprocessing unit. In other embodiments, processing unit 1204 may also beimplemented as a quad-core processing unit formed by integrating twodual-core processors into a single chip.

In various embodiments, processing unit 1204 can execute a variety ofprograms in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processor(s)1204 and/or in storage subsystem 1218. Through suitable programming,processor(s) 1204 can provide various functionalities described above.Computer system 1200 may additionally include a processing accelerationunit 1206, which can include a digital signal processor (DSP), aspecial-purpose processor, and/or the like.

I/O subsystem 1208 may include user interface input devices and userinterface output devices. User interface input devices may include akeyboard, pointing devices such as a mouse or trackball, a touchpad ortouch screen incorporated into a display, a scroll wheel, a click wheel,a dial, a button, a switch, a keypad, audio input devices with voicecommand recognition systems, microphones, and other types of inputdevices. User interface input devices may include, for example, motionsensing and/or gesture recognition devices such as the Microsoft Kinect®motion sensor that enables users to control and interact with an inputdevice, such as the Microsoft Xbox® 360 game controller, through anatural user interface using gestures and spoken commands. Userinterface input devices may also include eye gesture recognition devicessuch as the Google Glass® blink detector that detects eye activity(e.g., ‘blinking’ while taking pictures and/or making a menu selection)from users and transforms the eye gestures as input into an input device(e.g., Google Glass®). Additionally, user interface input devices mayinclude voice recognition sensing devices that enable users to interactwith voice recognition systems (e.g., Siri® navigator), through voicecommands.

User interface input devices may also include, without limitation, threedimensional (3D) mice, joysticks or pointing sticks, gamepads andgraphic tablets, and audio/visual devices such as speakers, digitalcameras, digital camcorders, portable media players, webcams, imagescanners, fingerprint scanners, barcode reader 3D scanners, 3D printers,laser rangefinders, and eye gaze tracking devices. Additionally, userinterface input devices may include, for example, medical imaging inputdevices such as computed tomography, magnetic resonance imaging,position emission tomography, medical ultrasonography devices. Userinterface input devices may also include, for example, audio inputdevices such as MIDI keyboards, digital musical instruments and thelike.

User interface output devices may include a display subsystem, indicatorlights, or non-visual displays such as audio output devices, etc. Thedisplay subsystem may be a cathode ray tube (CRT), a flat-panel device,such as that using a liquid crystal display (LCD) or plasma display, aprojection device, a touch screen, and the like. In general, use of theterm “output device” is intended to include all possible types ofdevices and mechanisms for outputting information from computer system1200 to a user or other computer. For example, user interface outputdevices may include, without limitation, a variety of display devicesthat visually convey text, graphics and audio/video information such asmonitors, printers, speakers, headphones, automotive navigation systems,plotters, voice output devices, and modems.

Computer system 1200 may comprise a storage subsystem 1218 thatcomprises software elements, shown as being currently located within asystem memory 1210. System memory 1210 may store program instructionsthat are loadable and executable on processing unit 1204, as well asdata generated during the execution of these programs.

Depending on the configuration and type of computer system 1200, systemmemory 1210 may be volatile (such as random access memory (RAM)) and/ornon-volatile (such as read-only memory (ROM), flash memory, etc.) TheRAM typically contains data and/or program modules that are immediatelyaccessible to and/or presently being operated and executed by processingunit 1204. In some implementations, system memory 1210 may includemultiple different types of memory, such as static random access memory(SRAM) or dynamic random access memory (DRAM). In some implementations,a basic input/output system (BIOS), containing the basic routines thathelp to transfer information between elements within computer system1200, such as during start-up, may typically be stored in the ROM. Byway of example, and not limitation, system memory 1210 also illustratesapplication programs 1212, which may include client applications, Webbrowsers, mid-tier applications, relational database management systems(RDBMS), etc., program data 1214, and an operating system 1216. By wayof example, operating system 1216 may include various versions ofMicrosoft Windows®, Apple Macintosh®, and/or Linux operating systems, avariety of commercially-available UNIX® or UNIX-like operating systems(including without limitation the variety of GNU/Linux operatingsystems, the Google Chrome® OS, and the like) and/or mobile operatingsystems such as iOS, Windows® Phone, Android® OS, BlackBerry® 10 OS, andPalm® OS operating systems.

Storage subsystem 1218 may also provide a tangible computer-readablestorage medium for storing the basic programming and data constructsthat provide the functionality of some embodiments. Software (programs,code modules, instructions) that when executed by a processor providethe functionality described above may be stored in storage subsystem1218. These software modules or instructions may be executed byprocessing unit 1204. Storage subsystem 1218 may also provide arepository for storing data used in accordance with the presentinvention.

Storage subsystem 1200 may also include a computer-readable storagemedia reader 1220 that can further be connected to computer-readablestorage media 1222. Together and, optionally, in combination with systemmemory 1210, computer-readable storage media 1222 may comprehensivelyrepresent remote, local, fixed, and/or removable storage devices plusstorage media for temporarily and/or more permanently containing,storing, transmitting, and retrieving computer-readable information.

Computer-readable storage media 1222 containing code, or portions ofcode, can also include any appropriate media known or used in the art,including storage media and communication media, such as but not limitedto, volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage and/or transmissionof information. This can include tangible computer-readable storagemedia such as RAM, ROM, electronically erasable programmable ROM(EEPROM), flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD), or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or other tangible computer readable media. This can also includenontangible computer-readable media, such as data signals, datatransmissions, or any other medium which can be used to transmit thedesired information and which can be accessed by computing system 1200.

By way of example, computer-readable storage media 1222 may include ahard disk drive that reads from or writes to non-removable, nonvolatilemagnetic media, a magnetic disk drive that reads from or writes to aremovable, nonvolatile magnetic disk, and an optical disk drive thatreads from or writes to a removable, nonvolatile optical disk such as aCD ROM, DVD, and Blu-Ray® disk, or other optical media.Computer-readable storage media 1222 may include, but is not limited to,Zip® drives, flash memory cards, universal serial bus (USB) flashdrives, secure digital (SD) cards, DVD disks, digital video tape, andthe like. Computer-readable storage media 1222 may also include,solid-state drives (SSD) based on non-volatile memory such asflash-memory based SSDs, enterprise flash drives, solid state ROM, andthe like, SSDs based on volatile memory such as solid state RAM, dynamicRAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, andhybrid SSDs that use a combination of DRAM and flash memory based SSDs.The disk drives and their associated computer-readable media may providenon-volatile storage of computer-readable instructions, data structures,program modules, and other data for computer system 1200.

Communications subsystem 1224 provides an interface to other computersystems and networks. Communications subsystem 1224 serves as aninterface for receiving data from and transmitting data to other systemsfrom computer system 1200. For example, communications subsystem 1224may enable computer system 1200 to connect to one or more devices viathe Internet. In some embodiments communications subsystem 1224 caninclude radio frequency (RF) transceiver components for accessingwireless voice and/or data networks (e.g., using cellular telephonetechnology, advanced data network technology, such as 3G, 4G or EDGE(enhanced data rates for global evolution), WiFi (IEEE 802.11 familystandards, or other mobile communication technologies, or anycombination thereof), global positioning system (GPS) receivercomponents, and/or other components. In some embodiments communicationssubsystem 1224 can provide wired network connectivity (e.g., Ethernet)in addition to or instead of a wireless interface.

In some embodiments, communications subsystem 1224 may also receiveinput communication in the form of structured and/or unstructured datafeeds 1226, event streams 1228, event updates 1230, and the like onbehalf of one or more users who may use computer system 1200.

By way of example, communications subsystem 1224 may be configured toreceive data feeds 1226 in real-time from users of social networksand/or other communication services such as Twitter® feeds, Facebook®updates, web feeds such as Rich Site Summary (RSS) feeds, and/orreal-time updates from one or more third party information sources.

Additionally, communications subsystem 1224 may also be configured toreceive data in the form of continuous data streams, which may includeevent streams 1228 of real-time events and/or event updates 1230, thatmay be continuous or unbounded in nature with no explicit end. Examplesof applications that generate continuous data may include, for example,sensor data applications, financial tickers, network performancemeasuring tools (e.g. network monitoring and traffic managementapplications), clickstream analysis tools, automobile trafficmonitoring, and the like.

Communications subsystem 1224 may also be configured to output thestructured and/or unstructured data feeds 1226, event streams 1228,event updates 1230, and the like to one or more databases that may be incommunication with one or more streaming data source computers coupledto computer system 1200.

Computer system 1200 can be one of various types, including a handheldportable device (e.g., an iPhone® cellular phone, an iPad® computingtablet, a PDA), a wearable device (e.g., a Google Glass® head mounteddisplay), a PC, a workstation, a mainframe, a kiosk, a server rack, orany other data processing system.

Due to the ever-changing nature of computers and networks, thedescription of computer system 1200 depicted in the figure is intendedonly as a specific example. Many other configurations having more orfewer components than the system depicted in the figure are possible.For example, customized hardware might also be used and/or particularelements might be implemented in hardware, firmware, software (includingapplets), or a combination. Further, connection to other computingdevices, such as network input/output devices, may be employed. Based onthe disclosure and teachings provided herein, a person of ordinary skillin the art will appreciate other ways and/or methods to implement thevarious embodiments.

In the foregoing specification, aspects of the invention are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

What is claimed is:
 1. A computer-implemented method comprising:providing an interface configured to enable a user to build anapplication, wherein building the application includes linking buildingblocks, and wherein the building blocks are configured to process datafrom data structures; receiving, via the interface, first inputcorresponding to a request to build a new building block; adding one ormore open input/output (I/O) features to the new building block, whereinthe one or more open I/O features comprise one or more open inputs tothe new building block or one or more open outputs from the new buildingblock; accessing a plurality of existing building blocks, wherein eachexisting building block of the plurality of existing building blockscorresponds to a data structure comprising one or more external I/Ofeatures; generating a menu object that facilitates a selection of oneor more building blocks from amongst the plurality of existing buildingblocks, wherein an identifier of each of the one or more building blocksis displayed when the menu object is selected; receiving second inputcorresponding to a selection, identified using the menu object, of aparticular building block of the plurality of existing building blocks;receiving third input corresponding to a selection of a particularexternal I/O feature of the particular building block to add to aparticular open I/O feature of the new building block; assigning theparticular external I/O feature of the particular building block to theparticular open I/O feature of the new building block, wherein assigningincludes storing assignment metadata in association with the newbuilding block, wherein the assignment metadata indicates a link fromthe particular external I/O feature to the particular open I/O feature,and wherein the link represents an input of the particular buildingblock being mapped to an output of the new building block or an outputof the particular building block being mapped to an input of the newbuilding block; and storing a definition of the new building block,wherein the definition comprises the one or more open I/O features andthe assignment metadata.
 2. The computer-implemented method of claim 1,wherein storing the definition of the new building block causes the newbuilding block to be available for selection using the menu object. 3.The computer-implemented method of claim 1, wherein the menu objectcorresponds to a drop down list, a search field with predictive text, aflyout menu, a dropline menu, and an accordion menu, or any combinationthereof.
 4. The computer-implemented method of claim 1, furthercomprising: identifying a type of an output of a first building block;identifying a type of an input of a second building block; andperforming a data truncation test to determine whether the type of theoutput of the first building block is compatible with the type of theinput of the second building block, and the data truncation testdetermining whether a transformation of data from the type of the outputof the first building block to the type of the input of the secondbuilding block truncates the data.
 5. The computer-implemented method ofclaim 4, wherein when the data truncation test indicates that atransformation truncates the data, then performing the data truncationtest further comprises: identifying one or more virtual transformationbuilding blocks that are configured to transform input data from a firstdata type to a second data type, the transformation of the input datafrom the first data type to the second data type not resulting intruncation of the input data; and combining the one or more virtualtransformation building blocks with the output of the first buildingblock or the input of the second building block.
 6. Thecomputer-implemented method of claim 4, wherein when the data truncationtest indicates that a transformation does not truncate the data, theoutput of the first building block is linked to the input of the secondbuilding block using the metadata, and an indication of the link isstored in the assignment metadata.
 7. The computer-implemented method ofclaim 1, wherein the one or more external I/O features comprise one ormore inputs that are defined for storage to the data structure and/orone or more outputs that are defined for retrieval from the datastructure.
 8. A system, comprising: one or more data processors; and anon-transitory computer-readable storage medium containing instructionswhich, when executed on the one or more data processors, cause the oneor more data processors to perform operations including: providing aninterface configured to enable a user to build an application, whereinbuilding the application includes linking building blocks, and whereinthe building blocks are configured to process data from data structures;receiving, via the interface, first input corresponding to a request tobuild a new building block; adding one or more open input/output (I/O)features to the new building block, wherein the one or more open I/Ofeatures comprise one or more open inputs to the new building block orone or more open outputs from the new building block; accessing aplurality of existing building blocks, wherein each existing buildingblock of the plurality of existing building blocks corresponds to a datastructure comprising one or more external I/O features; generating amenu object that facilitates a selection of one or more building blocksfrom amongst the plurality of existing building blocks, wherein anidentifier of each of the one or more building blocks is displayed whenthe menu object is selected; receiving second input corresponding to aselection, identified using the menu object, of a particular buildingblock of the plurality of existing building blocks; receiving thirdinput corresponding to a selection of a particular external I/O featureof the particular building block to add to a particular open I/O featureof the new building block; assigning the particular external I/O featureof the particular building block to the particular open I/O feature ofthe new building block, wherein assigning includes storing assignmentmetadata in association with the new building block, wherein theassignment metadata indicates a link from the particular external I/Ofeature to the particular open I/O feature, and wherein the linkrepresents an input of the particular building block being mapped to anoutput of the new building block or an output of the particular buildingblock being mapped to an input of the new building block; and storing adefinition of the new building block, wherein the definition comprisesthe one or more open I/O features and the assignment metadata.
 9. Thesystem of claim 8, wherein storing the definition of the new buildingblock causes the new building block to be available for selection usingthe menu object.
 10. The system of claim 8, wherein the menu objectcorresponds to a drop down list, a search field with predictive text, aflyout menu, a dropline menu, and an accordion menu, or any combinationthereof.
 11. The system of claim 8, further comprising: identifying atype of an output of a first building block; identifying a type of aninput of a second building block; and performing a data truncation testto determine whether the type of the output of the first building blockis compatible with the type of the input of the second building block,and the data truncation test determining whether a transformation ofdata from the type of the output of the first building block to the typeof the input of the second building block truncates the data.
 12. Thesystem of claim 11, wherein when the data truncation test indicates thata transformation truncates the data, then performing the data truncationtest further comprises: identifying one or more virtual transformationbuilding blocks that are configured to transform input data from a firstdata type to a second data type, the transformation of the input datafrom the first data type to the second data type not resulting intruncation of the input data; and combining the one or more virtualtransformation building blocks with the output of the first buildingblock or the input of the second building block.
 13. The system of claim11, wherein when the data truncation test indicates that atransformation does not truncate the data, the output of the firstbuilding block is linked to the input of the second building block usingthe metadata, and an indication of the link is stored in the assignmentmetadata.
 14. The system of claim 8, wherein the one or more externalI/O features comprise one or more inputs that are defined for storage tothe data structure and/or one or more outputs that are defined forretrieval from the data structure.
 15. A computer-program producttangibly embodied in a non-transitory machine-readable storage medium,including instructions configured to cause a data processing apparatusto perform operations including: providing an interface configured toenable a user to build an application, wherein building the applicationincludes linking building blocks, and wherein the building blocks areconfigured to process data from data structures; receiving, via theinterface, first input corresponding to a request to build a newbuilding block; adding one or more open input/output (I/O) features tothe new building block, wherein the one or more open I/O featurescomprise one or more open inputs to the new building block or one ormore open outputs from the new building block; accessing a plurality ofexisting building blocks, wherein each existing building block of theplurality of existing building blocks corresponds to a data structurecomprising one or more external I/O features; generating a menu objectthat facilitates a selection of one or more building blocks from amongstthe plurality of existing building blocks, wherein an identifier of eachof the one or more building blocks is displayed when the menu object isselected; receiving second input corresponding to a selection,identified using the menu object, of a particular building block of theplurality of existing building blocks; receiving third inputcorresponding to a selection of a particular external I/O feature of theparticular building block to add to a particular open I/O feature of thenew building block; assigning the particular external I/O feature of theparticular building block to the particular open I/O feature of the newbuilding block, wherein assigning includes storing assignment metadatain association with the new building block, wherein the assignmentmetadata indicates a link from the particular external I/O feature tothe particular open I/O feature, and wherein the link represents eitheran input of the particular building block being mapped to an output ofthe new building block or an output of the particular building blockbeing mapped to an input of the new building block; and storing adefinition of the new building block, and wherein the definitioncomprises the one or more open I/O features and the assignment metadata.16. The computer-program product of claim 15, wherein storing thedefinition of the new building block causes the new building block to beavailable for selection using the menu object.
 17. The computer-programproduct of claim 15, wherein the menu object corresponds to a drop downlist, a search field with predictive text, a flyout menu, a droplinemenu, and an accordion menu, or any combination thereof.
 18. Thecomputer-program product of claim 15, further comprising: identifying atype of an output of a first building block; identifying a type of aninput of a second building block; and performing a data truncation testto determine whether the type of the output of the first building blockis compatible with the type of the input of the second building block,and the data truncation test determining whether a transformation ofdata from the type of the output of the first building block to the typeof the input of the second building block truncates the data.
 19. Thecomputer-program product of claim 18, wherein when the data truncationtest indicates that a transformation truncates the data, then performingthe data truncation test further comprises: identifying one or morevirtual transformation building blocks that are configured to transforminput data from a first data type to a second data type, thetransformation of the input data from the first data type to the seconddata type not resulting in truncation of the input data; and combiningthe one or more virtual transformation building blocks with the outputof the first building block or the input of the second building block.20. The computer-program product of claim 18, wherein when the datatruncation test indicates that a transformation does not truncate thedata, the output of the first building block is linked to the input ofthe second building block using the metadata, and an indication of thelink is stored in the assignment metadata.